-
Notifications
You must be signed in to change notification settings - Fork 925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
service/header/core_listener: Fix bug where old block headers are spammed to headersub by bridge nodes #507
Conversation
If there are still TODOs, can we convert this to draft? |
How do you turn it back to draft mode @adlerjohn ? |
1a48afe
to
807f9d7
Compare
|
807f9d7
to
d312532
Compare
…e.Sleep for second before requesting sync state again
Appendix to my review. The assumption about fixing the issue has to be verified somehow. Manual verification is also fine and shouldn't be hard to setup |
Core_listener should still listen for new blocks while bridge node syncing and erasure code them but should not broadcast them yet. |
…locks even if syncing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a straightforward change and PR. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only thing that could be improved is related to:
Core_listener should still listen for new blocks while bridge node syncing and erasure code them but should not broadcast them yet.
Ideally this was captured by a test somehow (unit/swamp).
We found an issue with the approach there and after discussing plenty of solutions decided to change the solution here. Specifically, we decided to contribute to the PubSub for a specific feature that would allow us to solve the problem: libp2p/go-libp2p-pubsub#481 |
Closed in favour of #549 |
Resolves #499.